ci: auto-merge release-please PRs - #4
Merged
Conversation
Delegates to nullplatform/actions-nullplatform's auto-merge-release.yml (same setup already validated in services-postgresql-rds), so release PRs opened by release-please get merged automatically once checks pass, using a GitHub App token so the downstream release/tag workflow still fires.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
auto-merge-release-prworkflow (same setup validated end-to-end in ci: auto-merge release-please PRs services-postgresql-rds#5 / chore(main): release 0.1.0 #7), delegating to the reusable workflow in feat: add reusable auto-merge-release-pr workflow actions-nullplatform#83/#84.chore(main): release x.y.zPR opened by release-please once its checks pass, using a token minted from a GitHub App instead of the defaultGITHUB_TOKEN— a merge with the default token would not trigger the downstream push-triggeredreleaseworkflow (GitHub's Actions loop-prevention), so the tag/GitHub Release would never get created.Test plan
APP_RELEASE_ID/APP_RELEASE_PRIVATE_KEYorg secrets are visible to this repo.